-
Notifications
You must be signed in to change notification settings - Fork 953
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade PJM production parser #4871
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some comments on the new parts of the parser but I would like to take the oppertunity to clean up the old parts of the parser as well if you don't mind. I can get this done on friday.
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
Co-authored-by: Viktor Andersson <[email protected]>
@mathilde-daugy I cleaned up the usage of session a bit (I hope that's okay) but feel free to revert it if needed. |
Thanks Viktor :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small code feedbacks but otherwise looks great!
Issue
see Linear issue ELE-1281
Description
In the last data quality report, we noticed that there were many missing production data points for PJM. It seems like the current parser cannot collect data points at 4AM each day and sometimes for multiple hours.
I investigated and found that our production parser is a live parser so there is no way to get data for the missing points. There is an API however and it would be better to use it to get production (we get consumption forecast this way). This will enable us to backfill and get a more consistent dataset over time and potentially capture any data revisions.
This API can also be used to get LMP prices but would require a bit more work.
Preview
NA